1 The call's bearer mode cannot be changed to the specified bearer mode.
2 All call appearances on the specified address are currently in use.
3 The maximum number of outstanding call completions has been exceeded.
4 The maximum number of parties for a conference has been reached, or the requested number of parties cannot be satisfied.
5 The dialable address parameter contains dialing control characters that are not processed by the service provider.
7 The application requested an API version or version range that is either incompatible or cannot be supported by the Telephony API implementation and/or corresponding service provider.
8 The application requested an extension version range that is either invalid or cannot be supported by the corresponding service provider.
9 The file TELEPHON.INI cannot be read or understood properly by TAPI because of internal inconsistencies or formatting problems. For example, the [Locations], [Cards], or [Countries] section of TELEPHON.INI may be corrupted or inconsistent.
10 The line device is in use and cannot currently be configured, allow a party to be added, allow a call to be answered, allow a call to be placed, or allow a call to be transferred.
11 A specified address is either invalid or not allowed. If invalid, the address contains invalid characters or digits, or the deistination address contains dialing control characters (W, @, $, or ?) that are not supported by the service provider. If not allowed, the specified address is either not assigned to the specified line or is not valid for address redirection.
12 The specified address ID is either invalid or out of range.
13 The specified address mode is invalid.
14 dwAddressStates contains one or more bits that are not LINEADDRESSSTATE_ constants.
15 The application handle (such as specified by a hLineApp parameter) or the appliction registration handle is invalid.
16 The specified application name is invalid. If an application name is specified by the application, it is assumed that the string does not contain any non-displayable characters, and is zero-terminated.
17 The specified bearer mode is invalid.
18 The specified completion is invalid.
19 The specified call handle is not valid. For example, the handle is not NULL but does not belong to the given line. In some cases, the specified call device handle is invalid.
20 The specified call parameters are invalid.
21 The specified call privilege parameter is invalid.
22 The specified select parameter is invalid.
23 The current state of a call is not in a valid state for the requested operation.
24 The specified call state list is invalid.
25 The permanent card ID specified in dwCard could not be found in any entry in the [Cards] section in the registry.
26 The completion ID is invalid.
27 The specified call handle for the conference call is invalid or is not a handle for a conference call.
28 The specified consultation call handle is invalid.
29 The specified country code is invalid.
30 The line device has no associated device for the given device class, or the specified line does not support the indicated device class.
31 The specified digit list is invalid.
32 The specified digit mode is invalid.
33 The specified termination digits are not valid.
34 The dwFeature parameter is invalid.
35 The specified group ID is invalid.
36 The specified call, device, line device, or line handle is invalid.
37 The device configuration may not be changed in the current line state. The line may be in use by another application or a dwLineStates parameter contains one or more bits that are not LINEDEVSTATE_ constants. The LINEERR_INVALLINESTATE value can also indicate that the device is DISCONNECTED or OUTOFSERVICE. These states are indicated by setting the bits corresponding to the LINEDEVSTATUSFLAGS_CONNECTED and LINEDEVSTATUSFLAGS_INSERVICE values to 0 in the dwDevStatusFlags member of the LINEDEVSTATUS structure returned by the lineGetLineDevStatus function.
38 The permanent location ID specified in dwLocation could not be found in any entry in the [Locations] section in the registry.
39 The specified media list is invalid.
40 The list of media types to be monitored contains invalid information, the specified media mode parameter is invalid, or the service provider does not support the specified media mode. The media modes supported on the line are listed in the dwMediaModes field in the LINEDEVCAPS structure.
41 The number given in dwMessageID is outside the range specified by the dwNumCompletionuiMessageIDs field in the LINEADDRESSCAPS structure.
42 A parameter (such as dwTollListOption, dwTranslateOptions, dwNumDigits, or a structure pointed to by lpDeviceConfig) contains invalid values, a country code is invalid, a window handle is invalid, or the specified forward list parameter contains invalid information.
43 The specified park mode is invalid.
44 One or more of the specified pointer parameters (such as lpCallList, lpdwAPIVersion, lpExtensionID, lpdwExtVersion, lphIcon, lpLineDevCaps, and lpToneList) are invalid, or a required pointer to an output parameter is NULL.
45 An invalid flag or combination of flags was set for the dwPrivileges parameter.
46 The specified bearer mode is invalid.
47 The specified request mode is invalid.
48 The specified terminal mode parameter is invalid.
49 The specified terminal modes parameter is invalid.
50 Timeouts are not supported or the values of either or both of the parameters dwFirstDigitTimeout or dwInterDigitTimeout fall outside the valid range specified by the call's line-device capabilities.
51 The specified custom tone does not represent a valid tone or is made up of too many frequencies or the specified tone structure does not describe a valid tone.
52 The specified tone list is invalid.
53 The specified tone mode parameter is invalid.
54 The specified transfer mode parameter is invalid.
55 LINEMAPPER was the value passed in the dwDeviceID parameter, but no lines were found that match the requirements specified in the lpCallParams parameter.
56 The specified call is not a conference call handle or a participant call.
57 The specified device ID, which was previously valid, is no longer accepted because the associated device has been removed from the system since TAPI was last initialized. Alternately, the line device has no associated device for the given device class.
58 Either TAPIADDR.DLL could not be located or the telephone service provider for the specified device found that one of its components is missing or corrupt in a way that was not detected at initialization time. The user should be advised to use the Telephony Control Panel to correct the problem.
59 Insufficient memory to perform the operation, or unable to lock memory.
60 A Telephony Service Provider which does not support multiple instances is listed more than once in the [Providers] section in the registry. The application should advise the user to use the Telephony Control Panel to remove the duplicated driver.
61 There currently is no request pending of the indicated mode, or the application is no longer the highest-priority application for the specified request mode.
62 The application does not have owner privilege to the specified call(s).
63 The application is not registered as a request recipient for the indicated request mode.
64 The operation failed for an unspecified or unknown reason.
65 The operation is not available, such as for the given device or specified line.
66 The service provider currently does not have enough bandwidth available for the specified rate.
67 If TAPI reinitialization has been requested, for example as a result of adding or removing a Telephony service provider, then lineInitialize or lineOpen requests are rejected with this error until the last application shuts down its usage of the API (using lineShutdown), at which time the new configuration becomes effective and applications are once again permitted to call lineInitialize.
68 Insufficient resources to complete the operation. For example, a line cannot be opened due to a dynamic resource overcommitment.
69 The dwTotalSize field indicates insufficient space to contain the fixed portion of the specified structure.
70 A target for the call handoff was not found. This may occur if the named application did not open the same line with the LINECALLPRIVILEGE_OWNER bit in the dwPrivileges parameter of lineOpen. Or, in the case of media-mode handoff, no application has opened the same line with the LINECALLPRIVILEGE_OWNER bit in the dwPrivileges parameter of lineOpen and with the media mode specified in the dwMediaMode parameter having been specified in the dwMediaModes parameter of lineOpen.
71 The application invoking this operation is the target of the indirect handoff. That is, TAPI has determined that the calling application is also the highest priority application for the given media mode.
72 The operation was invoked before any application called lineInitialize.
73 The string containing user-to-user information exceeds the maximum number of bytes specified in the dwUUIAcceptSize, dwUUIAnswerSize, dwUUIDropSize, dwUUIMakeCallSize, or dwUUISendUserUserInfoSize field of LINEDEVCAPS, or the string containing user-to-user information is too long.
74 Invalid buffer.
75 Not enough memory.
76 End of file is reached.
77 The request could not be performed because of an I/O device error.
78 This error do not recognized
79 Serial Number you have entered is invalid.
80 Registration Code you have entered is invalid.
81 Initializing...
82 Dialing...
83 Sending Data...
84 An error ocurred during your registration. Please try later.
101 &About Boomerang Online Registration
102 Online Registration
103 This is the 30 days trial program version.
104 The trial period of this program has ended.\nPlease contact Boomerang Software to upgrade\nor purchase the latest full version.\n\nwww.boomerangsoftware.com\ntel: 617.489.3000\nFax: 617.489.1486
124 The First Name is required.
125 Registration
126 The Last Name field is required.
127 The Address field is required.
128 The City field is required.
129 The State field is required.
130 The Zip field is required.
131 The Country field is required.
132 The Telephone field is required.
142 Everything is OK
143 Current TAPI version invalid
144 TAPI32.DLL could not be located or it is corrupted
145 Either TAPIADDR.DLL could not be located. There is also the possibility that the telephone service provider for the specified device detected that one of its components is missing or corrupted. This may have not been detected at initialization time. You should use the Telephony Control Panel to correct the problem and try again.
146 Cannot initialize TAPI.
147 Cannot initialize line.
148 Cannot make call or dial out
149 Cannot hangup or terminate the call
150 Internal error encountered
151 Line is busy
152 Line disconnected by peer
153 Line does not answer
154 Error while reading or writing to serial port
155 Serial port is exclusively engaged or occupied by another process or program
156 Not enough memory to perform this function
157 Your telephony file TELEPHON.INI is corrupted or inconsistent
158 The given device is now unavailable
159 Insufficient resources to complete the operation.
160 Operation has been canceled
161 The specified address is blocked from being dialed on the specified call.
162 The line cannot be opened due to a \"persistent\" condition, such as that of a serial port being exclusively opened by another process.
